Organize and repair the WebMCP playground - #182

Summary

• set the RenderATL deck URL as the default PowerPoint import example
• remove LocalStudio's default PPTX byte ceiling for explicitly requested URL imports; constrained deployments can still configure maxFileSizeBytes
• keep authoring actions hidden until WebMCP discovery succeeds and organize the 14 supported tools into task-oriented sections
• show live operation progress directly below the playground action that started it
• feed WebMCP progress into LocalStudio's established editor state: deck translation status and slide processing, PowerPoint import overlay, and toolbar operation notices
• collapse each action's status, input, and result together while preserving completed results for reopening
• expose catalog and stock-media variants as submenus before showing their editable JSON and send controls
• remove the detailed-description action from the playground workflow while retaining the underlying agent tool
• let parallel-safe discovery actions such as stock media, catalogs, state, model status, preview, and operation status run while an exclusive authoring operation is active
• remove stale imported rich-text paragraphs after translation so the canvas renders translated text instead of the original PPTX runs
• make translation model preparation observable and verify that translation mutates the rendered slide
• persist full bounded semantic descriptions on slides while returning bounded previews from the operation
• assemble PDFs in a dedicated Web Worker with transferable buffers and per-page progress
• retain the worker-only image-generation runtime and expose its progress without blocking the editor UI
• remove publish_presentation from the hands-off authoring catalog while preserving the existing human sharing flow
• keep the embedded editor fixed while the action rail scrolls independently
• restore full editor iframe sizing after removing the old global-result stylesheet, with a browser geometry regression test
• split the WebMCP showcase's browser protocol/runtime orchestration from its rendering component
• remove the duplicate WebMCP editor-progress model, duplicate PDF worker protocol, duplicated browser-AI test setup, unused tool/status fields, redundant publishing-negation tests, and dead disabled-button selectors
• coalesce streaming PPTX download reports to visible percentage changes to avoid needless UI updates

Verification

• npm run lint (0 errors; one unrelated pre-existing unused-disable warning)
• npm run typecheck
• npm test (928 tests passed, 2 skipped across workspaces)
• npm run build:editor
• E2E_COVERAGE=0 vlt run test:e2e -- tests/e2e/webmcp/discover-tools.spec.ts (2 passed)
• manual browser verification: imported the 263 MB default PPTX into 61 slides, translated it, and confirmed slide 3 changed to Quem já construiu um aplicativo AI First? with no stale rich-text paragraphs
• manual browser verification: stock-media search stayed enabled during a live PowerPoint import while conflicting slide upsert stayed disabled
• browser regression: imported PPTX canvas pixels change after translation; status/input/result collapse together; submenu choices control JSON payloads; safe actions remain enabled during import
• npm run test:e2e:coverage:webmcp (3 passed)

WebMCP browser coverage: 37.48% bytes, 24.66% statements, 20.93% branches, 24.43% functions, and 36.22% lines.